Method and system for provisioning services on a communication network

ABSTRACT

A method for provisioning a service on a communication network includes receiving a service order comprising a service request. The service request relates to a service provided on a communication network. The method includes analyzing the service order to determine a plurality of network elements to provision to complete the service request and one or more network resources of the communication network required to complete the service request. The method includes retrieving a configuration profile for each of the plurality of network elements and reserving the one or more network resources of the communication network required to complete the service request. The method also includes preparing a service template for each of the plurality of network elements using the configuration profile for each of the plurality of network elements. The service templates are capable of being delivered to respective network elements for execution. The method also includes delivering each service template to a respective network element for execution to fulfill the service order.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to communication networks and,more particularly, to a method and system for provisioning services on acommunication network.

BACKGROUND OF THE INVENTION

Communication networks are used to provide a number of different typesof communication services to subscribers. Providers of these servicesutilize communication networks of varying size and complexity, many ofwhich include a plurality of different types of network elements thatcooperate to provide the communication services. Many such networkelements include their own management system for configuration,alteration and basic management of the network element.

SUMMARY OF THE INVENTION

The present invention provides a method and system for provisioning aservice on a communication network that substantially eliminates orreduces at least some of the disadvantages and problems associated withprevious methods and systems.

In accordance with a particular embodiment of the present invention, amethod for provisioning a service on a communication network includesreceiving a service order comprising a service request. The servicerequest relates to a service provided on a communication network. Themethod includes analyzing the service order to determine a plurality ofnetwork elements to provision to complete the service request and one ormore network resources of the communication network required to completethe service request. The method includes retrieving a configurationprofile for each of the plurality of network elements and reserving theone or more network resources of the communication network required tocomplete the service request. The method also includes preparing aservice template for each of the plurality of network elements using theconfiguration profile for each of the plurality of network elements. Theservice templates are capable of being delivered to respective networkelements for execution. The method also includes delivering each servicetemplate to a respective network element for execution to fulfill theservice order.

Preparing the service template for each of the plurality of networkelements may comprise correlating service parameters of the servicerequest, the configuration profile for each of the plurality of networkelements and the reserved one or more network resources; and populatingeach service template with task primitives associated with a respectivenetwork element. The method may also include analyzing the service orderto determine whether the service order relates to a legitimate serviceand updating a database of available network resources as the reservedone or more network resources are utilized. Delivering each servicetemplate to a respective network element for execution may comprisedelivering each service template to a respective network elementaccording to one or more schedule parameters. At least two of theplurality of network elements may utilize unique management systemsrequiring different types of task primitives to configure, alter ormanage the network elements. The service request may comprise asubscriber request to provision a new service for the subscriber on thecommunication network, a subscriber request to alter a current serviceprovisioned on the communication network for the subscriber or asubscriber request to resolve a problem for the subscriber with acurrent service provisioned on the communication network.

In accordance with another embodiment, a system for provisioning aservice on a communication network includes an interface operable toreceive a service order comprising a service request. The servicerequest relates to a service provided on a communication network. Thesystem includes a service provisioning manager coupled to the interface.The service provisioning manager is operable to analyze the serviceorder to determine a plurality of network elements to provision tocomplete the service request and one or more network resources of thecommunication network required to complete the service request. Theservice provisioning manager is also operable to retrieve aconfiguration profile for each of the plurality of network elements,reserve the one or more network resources of the communication networkrequired to complete the service request and prepare a service templatefor each of the plurality of network elements using the configurationprofile for each of the plurality of network elements. The servicetemplates are capable of being delivered to respective network elementsfor execution. The system also includes a delivery manager coupled tothe service provisioning manager, the delivery manager operable todeliver each service template to a respective network element forexecution to fulfill the service order.

Technical advantages of particular embodiments of the present inventioninclude a Universal Element Management Framework (UEMF) which isolatesmultiple element management systems from the service management layer ofa telecommunication provider's Operational Support System (OSS). Assuch, a telecommunication provider can make changes in network elementsand such changes may become transparent to the service management layer.

Particular embodiments include an element management system that mayreceive a service order relating to a service request for acommunication network, analyze the service order and configure,provision or otherwise manage the appropriate network elements tofulfill the service order. The element management system is able toprovision network elements of various vendors and types, even if suchnetwork elements have their own management systems requiring aparticular type of task primitives. Accordingly, operational costs andlabor associated with the fulfillment of service orders requiringprovisioning of various types of network elements are reduced.

Particular embodiments support end-to-end management oversight ofmultiple network elements from various vendors. This supports themeasurement and maintenance of service level agreements for the serviceorders provisioned on the various types of network elements positionedat the access, metro transport, edge and core of the telecommunicationprovider's network.

Particular embodiments support flow-thru provisioning in a singleelement management system, in which configuration templates (as opposedto operating system software blades) are used to automate provisioning.The template approach allows a user to make configuration templatechanges, as opposed to requiring a new “blade” whenever additionalfunctionality is released for a particular network element. Thus,particular embodiments provide a universal, multi-vendor elementmanagement system that is user-configurable which, as a result, maydecrease support and development costs for providing communicationservices.

Other technical advantages will be readily apparent to one skilled inthe art from the following figures, descriptions and claims. Moreover,while specific advantages have been enumerated above, variousembodiments may include all, some or none of the enumerated advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of particular embodiments of theinvention and their advantages, reference is now made to the followingdescriptions, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a system for providing subscriber communicationservices with an element management system, in accordance with aparticular embodiment;

FIG. 2 illustrates the element management system of FIG. 1, inaccordance with a particular embodiment; and

FIG. 3 illustrates a process flow diagram for provisioning a service ona communication network, in accordance with a particular embodiment.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a system 10 for providing subscriber communicationservices, in accordance with a particular embodiment. System 10 may beadministered, operated and managed by one or more organizationsproviding communication services to subscribers through one or morecommunication networks. Provided communication services may include, forexample, optical ethernet services, including but not limited topoint-to-point (E-Line services); point to multipoint (E-LAN services);managed L2 services, such as Frame Relay or ATM service interworkingwith Ethernet services and PWE3 aggregation services and managed IPservices, such as managed security services, managed VPN services andVirtual Private LAN services (VPLS). In the illustrated embodiment,system 10 includes a service management layer (SML) 12, a networkmanagement layer (NML) 14, an element management system (EMS) 16 andnetwork elements 20.

SML 12 manages service attributes for a particular service to ensure theservice meets a service level agreement. For example, a service providermay provide a T1 frame relay service or an E-line service with aspecific committed information rate (CIR) as part of a Service LevelAgreement. SML 12 monitors the service rate to ensure that the customeris receiving the appropriate service level.

NML 14 manages one or more network domains being utilized in theprovision of a service. NML 14 may comprise a “manager of managers”(MOM) that enables the creation of topological maps of networkarchitectures. For example, NML 14 may indicate, in graphical ornon-graphical form, the occurrence of various network events, such aswhen network elements are inoperable and when links are down. Inparticular embodiments, NML 14 may comprise a MOM, such as HP Open View(HPOV) or Netcool.

EMS 16 interacts with, provisions and otherwise manages network elements20 to provide communication services to subscribers of system 10.Particular functions of EMS 16 are discussed in further detail belowwith respect to FIG. 2.

Network elements 20 comprise various elements and components of thecommunication network being utilized, such as Core Routers, EdgeRouters, Multiservice Provisioning Platforms (MSPP), Multiserviceswitches, Optical Ethernet switches, Optical Add/Drop Multiplexers(OADMs) and Wave Division Multiplexing platforms (DWDM or CWDMplatforms). In some cases, network elements 20 may be manufactured bydifferent vendors and thus may be operated or managed by different,vendor-specific management systems. For example, network element 20 amanufactured be Vendor A may be managed by a Vendor A management systemunique from that used to manage network element 20 b manufactured byVendor B. The different management systems may require different typesof primitives to configure, alter and/or otherwise manage the respectivenetwork elements. The integration of each such management system intosystem 10 can be difficult and expensive, as a service provider usingthese network elements may have to maintain various software andhardware applications of different vendors and a separate middleware andworkflow management product to support the integration of thesedifferent vendor management systems into a seamless OSS architecture.

Particular embodiments provide an element management system that mayreceive a service order relating to a service request for acommunication network, analyze the service order and configure,provision or otherwise manager the appropriate network elements tofulfill the service order. The element management system is able toprovision network elements of various vendors and types, even if suchnetwork elements have their own management systems requiring particulartypes of task primitives. Accordingly, costs and labor associated withthe fulfillment of service orders requiring provisioning of varioustypes of network elements is reduced.

FIG. 2 illustrates element management system 16, in accordance with aparticular embodiment. EMS 16 comprises a service oriented architectureenabling a service provider to manage, change and provision networkelements and their configurations without having to worry about manualintegration of various management systems and without having to impactoperations at the service management and network management layers. EMS16 supports flow-thru provisioning in a single element managementsystem, in which configuration templates (as opposed to operating systemsoftware blades) are used to automate provisioning. The templateapproach allows a user to make configuration template changes, asopposed to requiring a new “blade” whenever additional functionality isreleased for a specific network element when providing communicationservices.

EMS 16 includes service provisioning manager 32, resourcemanager/controller 34, service order API 36, resource controller API 38and configuration delivery manager 40 connected to a gateway 42. EMS 16additionally includes OSS applications 44, service order GUI 46,resource/admin GUI 48, admin API 50, security server 52 and log server54. Particular components of EMS 16 may be connected to a bus 56, whichmay comprise a CORBA or XML bus in particular embodiments. In particularembodiments, components of EMS 16 may provide functionality through anAPI defined in, for example, CORBA IDL, SOAP or XML.

Service order API 36 receives service orders for provisioning throughEMS 16. Service order API 36 provides a northbound programming interfacefor the addition, deletion, modification and query of services providedto a subscriber through a communication network. Service orders may alsorelate to resolving problems with the current provisioning of services.

Service provisioning manager 32 enables service provisioning onspecified network elements. The process is highly customizable for therollout of new services, supporting the customization of network elementconfiguration through templates. The framework of service provisioningmanager 32 enables the dynamic plug in of network element taskprimitives at runtime without having to recompile the system. Serviceprovisioning manager 32 provides a common and flexible framework forvarious provisioning solutions to process service requests in aconsistent manner. Service provisioning manager 32 includes servicerequest manager 60, profile analyzer 62, profile manager 64, taskmanager 66, profiles 68, task primitives 70 and service templates 72.

Service request manager 60 manages a service request as it arrivesthrough a service order. Once a service request is received, servicerequest manager 60 determines whether it is a valid service for theparticular network and infrastructure associated with the subscriber orservice, as network architectures of different geographic regions, forexample, may offer different services. Service request manager 60 allowsa service provider to create business rules concerning the type ofservice requests the provider is willing to provision on a particularcommunication network.

Profile analyzer 62 analyzes a service order received across serviceorder API 36 to determine the network elements the service order islikely to touch or impact. This enables EMS 16 to determine the taskprimitives that may need to be used to create a configuration profilefor those particular network elements.

Profile manager 64 maintains profiles 68 of the network elements thatare needed to provide a defined service. As indicated above, the variousnetwork elements needed may utilize different, vendor-specificmanagement systems. Profile manager 64 enables the creation ofconfiguration templates operable for each of the network elements. Aconfiguration template includes configuration parameters that need to beadjusted in the specific management system of a network element to makethe necessary changes to network components to fulfill a service order.Profile manager 64 may match the configuration templates of particulardevices to a service order for which the devices may be provisioned.

Task manager 66 fills in templates with appropriate task primitives 70to complete a service template capable for dropping onto a networkelement for execution. Task primitives 70 are the actual commands usedto configure, alter and/or manage network elements. As indicated above,various network elements may understand different types of taskprimitives. The task manager ensures that the required resources for theservice to be provisioned are available before generating configurationfiles. For example, if required resources (such as IP addresses, VLANs,ports, etc.) are not available, then task manager 66 will return anerror. When resource or configuration data is changed due to a servicerequest, the profile for that service will invoke the proper taskprimitive for update in the resource repository of resource manager 34,further discussed below, and in the configuration of the involvednetwork elements.

Service templates 72 comprise comma delimited files with the networkelement management system commands needed to configure the networkelements for the provision of a particular service. Service templates 72comprise task primitives necessary to configure, modify or otherwiseprovision one or more network elements to fulfill a service order.

Resource manager 34 maintains an inventory of equipment and resourcesnecessary to provision services defined by service request manager 32.For example, a particular service may require a carrier VLAN and acertain amount of STS1s on a particular optical carrier to beprovisioned. The inventory of resource manager 34 includes the networkelements that need to be utilized to provide this service. Resourcemanager 34 is accessed by service provisioning manager 32 to determineavailability of particular resources required to fulfill a serviceorder. Resource manager 34 provides the capability to create, allocate,modify and delete resource and data elements. Resource manager 34 may becontrolled by resource controller API 38. In addition, as thefulfillment of service orders changes availability of resources andequipment for future service provisioning, resource manager 34automatically updates its data records to reflect such change inavailability.

Configuration delivery manager 40 transmits completed service templatesto gateway 42 for dropping onto network elements 20 for execution. Inparticular embodiments, configuration delivery manager 40 may transmitservice templates to gateway 42 at particular times, such as at aparticular time of the day. Thus, manager 40 allows a service providerto build specific business rules into when and how service templates areexecuted by network elements. These business rules may also account forcustomer preferences as to when and how service templates are executed.For example, a customer may prefer that changes be implemented between2:00 and 3:00 AM. Configuration deliver manager 40 can then scheduletransmission of service templates to network elements for execution atthis time.

Configuration delivery manager 40 is connected to gateway 42, which maydetermine whether a comma delimited service template file needs to beconverted to another format. If such a conversion is required, thengateway 42 may make the conversion. In particular embodiments, gateway42 may support, for example, conversion to Telnet, SSH and XML,depending on the technology a particular network element craft port mayunderstand. Gateway 42 may also detect syntax and parser errors duringdownload to a network element and may return error messages. Gateway 42may be integrated within EMS 16 or another system or deployed on a standalone appliance, for example, a 1U Linux appliance. From gateway 42, theservice templates are dropped onto network elements for execution.

Resource/Administrator GUI 48 provides a user-friendly graphical userinterface for creation and management of resources pertaining toelement, network and provisioning services. Thus, resource/administratorGUI 48 allows an operator of EMS 16 to make modifications to the system.The modifications may be made in case the system does not automaticallydetect changes in various parameters of a network through which servicesare provided (such as detecting when network elements are added to anetwork). Such modifications may include modifications to servicerequest manager 60, such as adding or deleting services providing on aparticular network; modifications to profile manager 62, such as addingor deleting configuration templates; and modifications to resourcemanager 34, such as adding or deleting resources available on thenetwork. Resource/Administrator GUI 48 may provide multiple views ofresources available in the system, each view representing a logicalgrouping or physical containment captured by EMS 16. In particularembodiments, the GUI may comprise a web browser GUI client and a JavaServlet-based GUI server.

Service order GUI 46 comprises a GUI that allows a customer servicerepresentative or other operator of EMS 16 to enter information topopulate service orders for fulfillment by the system.

OSS applications 44 provides an API for integration of legacyOperational Support System software applications into bus 56. Particularapplications which may be integrated may include legacy applicationsproviding for the entry of service order information.

Log server 54 provides functions for creation of log records for audittrails. Log server 54 may receive messages generated by other servers orclient programs and store them in an EMS 16 database. Log server 54 maythen generate from the messages log records of transactions across EMS16 for audit trails. In particular embodiments, the audit trails may beviewed through any suitable text editor, such as vi or emacs.

Security server 52 provides user authentication for security of EMS 16.Security server 52 may secure and authenticate any interaction from anyuser across bus 56, whether through resource/administrator GUI 48,service order GUI 46 or another application.

Administrator API 50 is used by an administrator of EMS 16 to setspecific user rights for various users of EMS 16 and its components,such as customer service representatives populating service orders andtechnical representatives modifying network resources or profileinformation through resource/administrator GUI 48. As an example, anadministrator may desire to give some users the ability to viewavailable resources, services and/or templates and to give other usersthe ability to make modifications to EMS 16 and its components.

It should be understood that components of EMS 16 may be implemented in,or in connection with, any number, type or form of processors,controllers, memory modules or other components. For example, suchcomponents may be implemented in one or more suitable computing devices,logic modules or resources adapted to execute various types of computerinstructions in various computer languages for implementing functionsavailable within the system. Implementations utilizing memory (forexample, to store profiles 68, task primitives 70 and service templates72) may include any form of volatile or nonvolatile memory including,without limitation, magnetic media, optical media, random access memory(RAM), read only memory (ROM), removable media or any other suitablelocal or remote memory component. Components of EMS 16 may be combinedand/or divided for processing according to particular needs or desireswithin the scope of the present invention.

FIG. 3 is a process flow diagram for provisioning a service on acommunication network, in accordance with a particular embodiment. Atstep 100, a service order is received that relates to a service providedon a communication network. Any number of types of systems may createthe service order. For example, in particular embodiments a Siebelsystem may create the service order received at step 100. At step 102,the received service order flows through an API, such as service orderAPI 36 of EMS 16 of FIG. 2. The service order flows to a service requestmanager at step 104. At step 106, service request manager determineswhether the service order relates to a legitimate service. Thedetermination may include, for example, whether the service that is thesubject of the service order is provided by or available at theparticular network to which the service order relates. If the serviceorder does not relate to a legitimate service, then the method proceedsto step 108, where a message indicating that the service is notavailable may be transmitted to an originator of the service order.

If it is determined that the service order relates to a legitimateservice, then the service order flows to a profile analyzer at step 110where the service order is analyzed. The profile analyzer determineswhat network elements must be provisioned to fulfill the service orderand what network resources must be available for such fulfillment. Todetermine the network elements that must be provisioned, the profileanalyzer interacts with a profile manager at step 112. The profilemanager includes configuration profiles and other information and datarelating to network elements of the applicable network. The profileanalyzer also interacts with the resource manager at step 114 to reserveresources required to fulfill the service order. The resource managerincludes a database of network resources and updates their availabilityas the network is used.

After the profile analyzer determines the needed network elements andreserves required resources for fulfilling the service order, theprocess proceeds to a task manager at step 116. The task managerinteracts with task primitives at step 118 to create one or more servicetemplates at step 120. To create the service template, the task managercorrelates service parameters of the service order, templates of thenetwork elements that need to be utilized or provisioned and thereserved network resources. The service template comprises a finalconfiguration template that may be executed by a network element. Insome embodiments, the service template may comprise a comma delimitedformat.

If multiple network elements must be provisioned, configured orotherwise utilized to fulfill the service order, then multiple servicetemplates may be created such that each such network element receives aservice template that it understands for execution. In particularembodiments, multiple service templates may be created to provision,configure or otherwise utilize multiple network elements of variousbrands or types to fulfill a particular service order according to therespective individual management systems of those network elements.

The service template flows to a configuration delivery manager at step122. The configuration delivery manager delivers the service templatebased on rules that a service manager may create that govern thedelivery of the service template. Such rules may be based upon, forexample, time or manner of delivery of the service template. Inparticular embodiments, the configuration delivery manager may alsoperform an audit check on the service delivery to ensure legitimacy atstep 122. At step 124, the configuration delivery manager delivers theservice template to a gateway which may convert the template to anappropriate format, such as Telnet, SSH or XML. At step 126, the gatewaydelivers the service template to a network element for execution. Thenetwork element's execution of the service template fulfills the serviceorder. As indicated above, in particular embodiments a service order mayrequire use, modification or provisioning of multiple network elements.In such instance, multiple service templates may be created forexecution at respective network elements. In some embodiments, once theservice template is executed, the network element performing theexecution may transmit a signal back to the element management systemindicating successful or unsuccessful execution. In the event ofunsuccessful execution, the configuration delivery manager will executea roll back order to the network elements which were successfullyexecuted and send an error code back to EMS 16.

Some of the steps illustrated in FIG. 3 may be combined, modified ordeleted where appropriate, and additional steps may also be added to thediagram. Additionally, steps may be performed in any suitable orderwithout departing from the scope of the invention.

Although the present invention has been described in detail withreference to particular embodiments, it should be understood thatvarious other changes, substitutions, and alterations may be made heretowithout departing from the spirit and scope of the present invention.For example, although the present invention has been described withreference to a number of elements included within element managementsystem 16, including service provisioning manager 32 and resourcemanager/controller 34, these elements may be combined, rearranged orpositioned in order to accommodate particular network or routingarchitectures or specific customer requirements. In addition, any ofthese elements included within element management system 16 may beprovided as separate external components where appropriate. The presentinvention contemplates great flexibility in the arrangement of theseelements as well as their internal components.

Numerous other changes, substitutions, variations, alterations andmodifications may be ascertained by those skilled in the art and it isintended that the present invention encompass all such changes,substitutions, variations, alterations and modifications as fallingwithin the spirit and scope of the appended claims.

1. A method for provisioning a service on a communication network,comprising: receiving a service order comprising a service request, theservice request relating to a service provided on a communicationnetwork; analyzing the service order to determine: a plurality ofnetwork elements to provision to complete the service request; and oneor more network resources of the communication network required tocomplete the service request; retrieving a configuration profile foreach of the plurality of network elements; reserving the one or morenetwork resources of the communication network required to complete theservice request; preparing a service template for each of the pluralityof network elements using the configuration profile for each of theplurality of network elements, the service templates capable of beingdelivered to respective network elements for execution; and deliveringeach service template to a respective network element for execution tofulfill the service order.
 2. The method of claim 1, wherein preparingthe service template for each of the plurality of network elementscomprises: correlating service parameters of the service request, theconfiguration profile for each of the plurality of network elements andthe reserved one or more network resources; and populating each servicetemplate with task primitives associated with a respective networkelement.
 3. The method of claim 1, further comprising analyzing theservice order to determine whether the service order relates to alegitimate service.
 4. The method of claim 1, further comprisingupdating a database of available network resources as the reserved oneor more network resources are utilized.
 5. The method of claim 1,wherein delivering each service template to a respective network elementfor execution comprises delivering each service template to a respectivenetwork element according to one or more schedule parameters.
 6. Themethod of claim 1, further comprising converting one or more of theservice templates to a separate format for delivery to a respectivenetwork element.
 7. The method of claim 1, wherein at least two of theplurality of network elements utilize unique management systemsrequiring different types of task primitives to configure, alter ormanage the network elements.
 8. The method of claim 1, wherein executionof at least one of the service templates at a respective network elementcomprises an alteration of a configuration of the respective networkelement.
 9. The method of claim 1, wherein the service request comprisesa subscriber request to provision a new service for the subscriber onthe communication network.
 10. The method of claim 1, wherein theservice request comprises a subscriber request to alter a currentservice provisioned on the communication network for the subscriber. 11.The method of claim 1, wherein the service request comprises asubscriber request to resolve a problem for the subscriber with acurrent service provisioned on the communication network.
 12. A systemfor provisioning a service on a communication network, comprising: aninterface operable to receive a service order comprising a servicerequest, the service request relating to a service provided on acommunication network; a service provisioning manager coupled to theinterface, the service provisioning manager operable to: analyze theservice order to determine: a plurality of network elements to provisionto complete the service request; and one or more network resources ofthe communication network required to complete the service request;retrieve a configuration profile for each of the plurality of networkelements; reserve the one or more network resources of the communicationnetwork required to complete the service request; and prepare a servicetemplate for each of the plurality of network elements using theconfiguration profile for each of the plurality of network elements, theservice templates capable of being delivered to respective networkelements for execution; and a delivery manager coupled to the serviceprovisioning manager, the delivery manager operable to deliver eachservice template to a respective network element for execution tofulfill the service order.
 13. The system of claim 12, wherein a serviceprovisioning manager operable to prepare the service template for eachof the plurality of network elements comprises a service provisioningmanager operable to: correlate service parameters of the servicerequest, the configuration profile for each of the plurality of networkelements and the reserved one or more network resources; and populateeach service template with task primitives associated with a respectivenetwork element.
 14. The system of claim 12, wherein the serviceprovisioning manager is further operable to analyze the service order todetermine whether the service order relates to a legitimate service. 15.The system of claim 12, further comprising a resource manager coupled tothe service provisioning manager, the resource manager operable toupdate a database of available network resources as the reserved one ormore network resources are utilized.
 16. The system of claim 12, whereina delivery manager operable to deliver each service template to arespective network element for execution comprises a delivery manageroperable to deliver each service template to a respective networkelement according to one or more schedule parameters.
 17. The system ofclaim 12, further comprising a gateway coupled to the delivery manager,the gateway operable to convert one or more of the service templates toa separate format for delivery to a respective network element.
 18. Thesystem of claim 12, wherein at least two of the plurality of networkelements utilize unique management systems requiring different types oftask primitives to configure, alter or manage the network elements. 19.The system of claim 12, wherein execution of at least one of the servicetemplates at a respective network element comprises an alteration of aconfiguration of the respective network element.
 20. The system of claim12, wherein the service request comprises a subscriber request toprovision a new service for the subscriber on the communication network.21. The system of claim 12, wherein the service request comprises asubscriber request to alter a current service provisioned on thecommunication network for the subscriber.
 22. The system of claim 12,wherein the service request comprises a subscriber request to resolve aproblem for the subscriber with a current service provisioned on thecommunication network.
 23. Software embodied in a computer readablemedium, the computer readable medium comprising code operable to:receive a service order comprising a service request, the servicerequest relating to a service provided on a communication network;analyze the service order to determine: a plurality of network elementsto provision to complete the service request; and one or more networkresources of the communication network required to complete the servicerequest; retrieve a configuration profile for each of the plurality ofnetwork elements; reserve the one or more network resources of thecommunication network required to complete the service request; preparea service template for each of the plurality of network elements usingthe configuration profile for each of the plurality of network elements,the service templates capable of being delivered to respective networkelements for execution; and deliver each service template to arespective network element for execution to fulfill the service order.24. The medium of claim 23, wherein code operable to prepare the servicetemplate for each of the plurality of network elements comprises codeoperable to: correlate service parameters of the service request, theconfiguration profile for each of the plurality of network elements andthe reserved one or more network resources; and populate each servicetemplate with task primitives associated with a respective networkelement.
 25. The medium of claim 23, wherein the code is furtheroperable to analyze the service order to determine whether the serviceorder relates to a legitimate service.
 26. The medium of claim 23,wherein the code is further operable to update a database of availablenetwork resources as the reserved one or more network resources areutilized.
 27. The medium of claim 23, wherein code operable to delivereach service template to a respective network element for executioncomprises code operable to deliver each service template to a respectivenetwork element according to one or more schedule parameters.
 28. Themedium of claim 23, further comprising code operable to convert one ormore of the service templates to a separate format for delivery to arespective network element.
 29. The medium of claim 23, wherein at leasttwo of the plurality of network elements utilize unique managementsystems requiring different types of task primitives to configure, alteror manage the network elements.
 30. The medium of claim 23, whereinexecution of at least one of the service templates at a respectivenetwork element comprises an alteration of a configuration of therespective network element.
 31. The medium of claim 23, wherein theservice request comprises a subscriber request to provision a newservice for the subscriber on the communication network.
 32. The mediumof claim 23, wherein the service request comprises a subscriber requestto alter a current service provisioned on the communication network forthe subscriber.
 33. The medium of claim 23, wherein the service requestcomprises a subscriber request to resolve a problem for the subscriberwith a current service provisioned on the communication network.